Disable or control purging

I'm trying to determine if there is a way to disable or control the ability to purge deleted objects for certain users or groups. In my organization, it would be ideal if only a handful of users had the ability to purge objects in order to prevent the accidental elimination of requirements from the database. As a worst case scenario in this situation, a standard user goes about making changes to a module (deletions, additions, etc) and then accidentally purges, or purges with the assumption that they have identified the correct objects for deletion. After the fact, he or she realizes that one of the objects was a requirement should not have been deleted, and the only way to restore it is via an archive restore or a baseline, the latter requiring all objects to be relinked.

Is there a way to control this functionality? Or am I going about this all wrong? Is there some innate DOORS functionality that would make this kind of contol unecessary?
mgeb - Thu Aug 02 12:48:12 EDT 2012

Re: Disable or control purging
SystemAdmin - Mon Mar 11 05:11:55 EDT 2013

restricting the access rights to "Delete" is the best option you have. Do read about propagating access rights from the help section and you may find it useful.

Re: Disable or control purging
llandale - Mon Mar 11 13:55:58 EDT 2013

SystemAdmin - Mon Mar 11 05:11:55 EDT 2013
restricting the access rights to "Delete" is the best option you have. Do read about propagating access rights from the help section and you may find it useful.

Yes, but then they cannot "delete" an unwanted object.

I'd be tempted to install some override for "hardDelete(Object)" and "delete(Object)" in the top context; perhaps with a database wide post-module-open trigger: run an "eval_()" of some odd global variable; if it comes back with interpret errors then issue an "evalTop_()" of the override functions and your odd global variable.

Re: Disable or control purging
Tony_Goodman - Mon Mar 18 11:41:13 EDT 2013

You need to educate your users or lock down the database.
Standard users NEVER need to purge objects, and should never do so.

Purging should only be done by people that know what they are doing and only after a baseline.

I would be tempted to remove delete access and instead instruct the users to mark an object as deleted using an attribute.
Once the module has been reviewed and agreed, and baselined, then you can soft delete the objects marked for deletion. No need to purge until after a later baseline.

Tony Goodman, www.smartdxl.com

Re: Disable or control purging
Tony_Goodman - Mon Mar 18 11:42:26 EDT 2013

Tony_Goodman - Mon Mar 18 11:41:13 EDT 2013
You need to educate your users or lock down the database.
Standard users NEVER need to purge objects, and should never do so.

Purging should only be done by people that know what they are doing and only after a baseline.

I would be tempted to remove delete access and instead instruct the users to mark an object as deleted using an attribute.
Once the module has been reviewed and agreed, and baselined, then you can soft delete the objects marked for deletion. No need to purge until after a later baseline.

Tony Goodman, www.smartdxl.com

In fact it is generally good practice to never actually delete requirements, especially from a specification that has previously been issued. Mark as deleted, filter to hide them etc.

Tony Goodman, www.smartdxl.com